Recording and reporting of driving characteristics using wireless mobile device

ABSTRACT

A system and method for monitoring a vehicle uses a wireless mobile device. The wireless mobile device, such as a cell phone, smart phone, PDA, etc., includes some of the hardware that could be utilized to monitor and analyze data and transmit the data (or summaries, statistics or analyses of the data) to a central server. This can greatly reduce the overall cost of the system. The data can be used to determine an insurance rate or as a speed probe for creating traffic maps, for example.

This application claims priority to U.S. Provisional Applications Ser. Nos. 60/939,844 and 61/041,944 filed May 23, 2007 and Apr. 3, 2008, respectively.

BACKGROUND OF THE INVENTION

This invention relates to a device and method for recording driving characteristics. More importantly, this invention relates to a method and device for recording driving characteristics utilized to monitor and compile vehicle usage data for determining an insurance premium.

It has been proposed that vehicle insurance companies could determine insurance premiums based upon information gathered by in-vehicle sensors that indicate where the vehicle was driven, how fast the vehicle was driven, times of day and days of the week, etc. Generally, these systems have required a relatively significant cost for the required in-vehicle hardware.

SUMMARY OF THE INVENTION

The present invention provides a system and method for monitoring a vehicle using a wireless mobile device. The wireless mobile device, such as a cell phone, smart phone, PDA, etc., includes some of the hardware which could be utilized to monitor and analyze data and transmit the data (or summaries, statistics or analyses of the data) to a central server. This greatly reduces the overall cost of the system and provides other benefits.

These and other features of the application can be best understood from the following specification and drawings, the following of which is a brief description.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic view of the vehicle monitoring system according to the present invention.

FIG. 2 is a more detailed schematic of the vehicle unit and mobile unit of FIG. 1.

FIG. 3 illustrates one technique for determining vehicle location based upon cell phone triangulation.

FIG. 4 illustrates a risk coding algorithm that could be used with the monitoring system of FIG. 1 and FIG. 2.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

Referring to FIG. 1, a system 10 for monitoring a vehicle 12 includes a vehicle unit 14 installed in the vehicle 12 and a mobile unit 16, which is carried by a user. The vehicle unit 14 receives power from the vehicle 12 and receives vehicle operating data from a vehicle bus 18, such as an OBD-II port. The vehicle unit 14 and mobile unit 16 communicate with one another wirelessly via any encrypted or secure wireless communication protocol, such as Bluetooth. As will be explained in more detail below, in general, the system 10 determines a location of the vehicle, speed, acceleration, engine conditions, etc. and transmits this data via cell towers 20 (or other wireless transceivers) to a server 22. The server 22 collects and analyzes the data from the system 10 and forwards summaries, statistics and/or analyses, or rate levels based upon the data, to an insurance server 24, which determines an insurance premium for the vehicle 12 based upon the information from server 22.

The system 10 may sample and send the data to the server 22 periodically (between once per second to once per minute or so), or the system 10 may accumulate data and then send the data to the server 22 periodically (every few minutes to every hour). Alternatively, the system 10 may accumulate the data and then process the data to generate summaries (e.g. trip summaries), statistics (averages, etc) and/or indications of events, such as exceeded speed limits, hard accelerations, hard braking, hard lateral accelerations, changes in rate level geographical locations, etc. Additionally, or alternatively, the system 10 could transmit to the server 22 as triggered by the occurrence of such events—accidents in particular—and additional events, such as engine start/engine stop. The server 22 could also send a request to the system 10 for information (such as a full upload of all collected information, summaries, or other information). For example, if the user reports that the vehicle 12 is stolen, then the server 22 can send requests to the system 10 to transmit the location, speed and heading of the vehicle 12.

An optional user computer 28 connects to the server 22 via a wide area network, such as the internet, for uploading data from the system 10 (or summaries, statistics and/or analyses of the data) or downloading such information from the server 22. The user computer 28 can also display to the user usage summaries, statistics and analyses indicating to the user the cost of the insurance premium, suggestions for reducing the insurance premium, trip summaries, other vehicle events, etc. Alternatively, mobile devices 16 with sufficient computing power and displays could perform these functions just as a user computer 28.

The location of the vehicle 12 may optionally be determined by the system 10 based upon the information from GPS satellites 26 or by the cell towers 20.

As shown in FIG. 2, the hardware and software within the system 10 can be distributed between the vehicle unit 14 and the mobile unit 16 in many different ways. Preferably, if the user's mobile unit 16 (i.e. the user's cell phone, smart phone, PDA, etc.) includes more hardware and capability, more of the functions are shifted to the mobile unit 16, such that the hardware on the vehicle unit 14 can be reduced, thus saving cost and simplifying the installation. The vehicle unit 14 is connected to the vehicle bus 18 from which it can receive the vehicle identification number (VIN), and vehicle operating data, such as odometer, speed, and vehicle diagnostic information. The vehicle unit 14 includes a CPU 30 having memory 32 storing data and instructions for performing the functions described herein. The vehicle unit 14 further includes a wireless communication circuit 34, such as a Bluetooth communication circuit (other communication protocols could also be utilized). The vehicle unit 14 further includes (optionally) an accelerometer 36, which is preferably a three-axis accelerometer for measuring vehicle acceleration, including lateral acceleration of the vehicle. Optionally, the vehicle unit 14 includes a cell phone communication circuit 38, such as a GPRS circuit or other cell or satellite communication protocol. Optionally, the vehicle unit 14 includes a removable storage 40, such as an SD card, USB key, etc. such that data can be transferred between the vehicle unit 14 and the user computer 28 (FIG. 1).

Again, the mobile unit 16 is preferably a cell phone, smart phone, or wireless-capable PDA or similar portable electronic device with a processor and wireless communication ability. The mobile unit 16 includes a CPU 44 having a memory 46 for storing data and instructions, which when executed by the CPU 44 perform the features described herein. The mobile unit 16 includes a wireless communication circuit 48, such as a Bluetooth communication circuit or other wireless communication protocol. The mobile unit 16 includes a cell phone circuit 50, such as a GPRS circuit or other wireless cell or satellite phone communication circuitry. The mobile unit 16 may optionally include a GPS receiver 52, which indicates to the CPU 44 a current location of the mobile unit 16 relative to Earth. Part of the benefit of the present invention is that many such commonly-available mobile units 16 already include much of this hardware and have sufficient storage and processing power to perform the functions described herein.

In one implementation of the embodiment shown in FIG. 2, the CPU 30 of the vehicle unit 14 accumulates vehicle operating data from the vehicle bus 18, the accelerometer 36, and from the mobile unit 16. When the vehicle unit 14 detects the presence of the mobile unit 16 and recognizes the mobile unit 16 as a previously registered mobile unit 16 associated with an authorized, insured user of the vehicle 12, the vehicle unit 14 identifies an associated user of the mobile unit 16 as the current driver of the vehicle 12 and begins communicating with the mobile unit 16. If more than one registered mobile unit 16 are detected (e.g. a husband and wife traveling together), the vehicle unit 14 assumes that the user designated the primary driver is driving the vehicle 12 (optionally subject to manual override via a user interface on the mobile units 16). Mobile units 16 could be registered for more than one vehicle 12 (again, e.g., a husband and wife both registered on each other's vehicles 12).

The vehicle unit 14 receives GPS location information from the GPS receiver 52 of the mobile unit 16 (if included). Alternatively, or when GPS is not available, the location of the mobile unit 16 can be determined based upon the communication circuit 50 in the mobile unit 16 being detected by nearby cell towers 20 using cell tower triangulation (such techniques are well known). This location is provided to the mobile unit 16 and in turn relayed to the vehicle unit 14. Thus, the mobile unit 16 can provide any or all of the following information to the vehicle unit 14: GPS location, cell tower triangulation location, identification of a driver of the vehicle 12 (by identifying the mobile unit 16). The mobile unit 16 also provides a way for the vehicle unit 14 (if not provided with its own cell communication circuit 38) a way to send information to the server 22 via the cell tower 20. If the vehicle unit 14 is provided with a cellular communication circuit 38, then the location of the vehicle unit 14 can be provided directly based upon cell tower triangulation.

FIG. 3 illustrates a method for improving the accuracy of the cell tower triangulation location determination. As is known, the location of the mobile device 16 can be determined by the server 22 via a plurality of cell towers 20 using triangulation. This location is generally accurate only to within a radius of two-hundred feet (currently). As the vehicle 12 is driven by a driver carrying a mobile device 16 along roads 60, 62, the server 22 first determines the mobile device 16 to be within a general area 64 having a center A. This is done using triangulation from cell towers 20. At some later time, the position of the mobile unit 16 is determined to be within general area 66 having a center B utilizing triangulation from cell towers 20 (which may be the same towers 20, a subset of towers 20, completely different towers 20 or some same and some different towers 20).

During that time between point A and point B, the vehicle bus 18 indicates to the vehicle unit 14 that the vehicle 12 has traveled a distance d. The travel distance d is very accurate, and is much more accurate than the triangulated positions A, B. However, using the raw triangulation data used to calculate the positions A, B in combination with the relatively accurate travel distance d (and, optionally, speed and acceleration, all of which are accurately measured on the vehicle) the positions solutions A, B can be recalculated with significantly increased accuracy. Preferably, the calculation is done using the same cell towers 20 for position A and position B, but it does not have to be the same cell towers 20. To the extent that the road is curved, the curved segments will be approximated as a sequence of linear segments.

Referring to FIG. 4, for any of the embodiments or alternatives described herein, the data may be gathered and used as shown. Generally, a risk coding algorithm 70 receives the vehicle operating data, such as vehicle location (as determined by GPS or cell tower triangulation or the improved cell tower triangulation calculation described above or any other sensors), vehicle speed, current speed limit (as determined for the current vehicle location from a map database of speed limits), time of day, day of the week, hard accelerations (including hard braking, lateral accelerations), etc. Risk coding algorithm 70 could be performed on server 22 (after which the underlying data may be discarded to preserve privacy), on the vehicle unit 14, on the mobile unit 16 or on the user computer 28.

A risk map database 72 includes risk ratings for a plurality of geographical areas (e.g. zip codes). The risk map database 72 may include more than one risk rating for each geographical area, such that different risk ratings are applicable for different times of day or days of the week. The risk rating mapping is many to one, meaning that many different geographical areas will have the same risk rating.

In a simplest example, the risk code generated by the risk-coding algorithm could be based solely on time spent in each geographical area and the associated risk ratings for those geographical areas. The risk code could be simply an indication of how much time (or what times of day) the vehicle was in areas of certain risk ratings. For example, the risk code could indicate that the vehicle was in a zone of risk rating 4 between 4:00 and 5:00, in a zone of risk rating 10 between 5:00 and 5:35, and in a zone of risk rating 1 between 5:35 and 6:00. This resultant risk code information could be used by the insurance company to determine insurance rates, while preserving some privacy for the user. Because the risk ratings are many-to-one, it is not possible to determine exactly where the user was during these times.

In another example, additional information, such as speed (or speed as compared to current speed limit), time of day, day of the week, hard acceleration information, etc. could all be input into the risk-coding algorithm 70. The durations of each condition affecting insurance cost are also used in the risk-coding algorithm 70. The resultant risk code output is simply an associated insurance cost factor. The insurance cost charged to the user for the vehicle is then determined by the insurance server 24 as a function of the risk code and optionally any other permanent information stored on the insurance server 24 (such as the user's age, the type of vehicle, the user's driving record, etc). By combining several different types of information in the risk-coding algorithm 70 prior to sending the risk code to the insurance server 24 (or, if calculated on the server 24, prior to storing on the server 24 and discarding the underlying data), the specific information that may intrude on the user's privacy is obscured.

Returning back to FIG. 2, in another implementation of the embodiment shown in FIG. 2, the accumulation of vehicle operating data and generation of summaries, statistics and/or analyses could be primarily performed on the mobile unit 16 instead of the vehicle unit 14. Thus, once the mobile unit detects that it is near the vehicle unit 14, it begins receiving vehicle operating data from the vehicle unit 14, including odometer, speed, acceleration (which may be calculated by the vehicle unit 14 based upon speed). The mobile unit 16 identifies the vehicle 12 in which it is operating based upon the VIN received from the vehicle unit 14. In this implementation, the mobile unit 16 may directly have its location via the GPS receiver 52 and/or cell tower triangulation of its cell phone communication circuit 50 (as transmitted by server 22). This could minimize the amount of hardware necessary in the vehicle unit 14 and reduce the competing power necessary for the CPU 30 in the vehicle unit 14.

In the event that the vehicle 12 is driven in the absence of the mobile unit 16 (or some other registered, authorized mobile unit 16), the vehicle unit 14 first notifies the unknown driver audibly and/or via LED lights that the mobile unit 16 is not connected (for example, in case the mobile unit 16 is simply off, or the driver has simply forgotten the mobile unit 16 and can still retrieve it). The vehicle unit 14 then accumulates in memory 32 as much vehicle operating data as it has available as the vehicle 12 is driven. For example, the vehicle unit 14 can accumulate engine-on and engine-off occurrences, each of which is designated as a “trip.” The vehicle unit 14 also accumulates speeds during each trip from the vehicle bus 18, and distance traveled during each trip. If the vehicle unit 14 includes an accelerometer 36, the vehicle unit 14 records accelerations during the trips. When the mobile unit 16 is subsequently brought into the proximity of the vehicle unit 14, the mobile unit 16 compares previously stored information from the vehicle unit 14 to the currently stored information on the vehicle unit 14, including current odometer reading. The mobile unit 16 also compares the last stored location of the vehicle unit 14 that was stored on the mobile unit 16 and compares it to the currently determined location of the vehicle unit 14, as determined by the mobile unit 16. Discrepancies indicate to the mobile unit 16 that the vehicle 12 was operated without the mobile unit 16. In that case, the mobile unit 16 retrieves the information accumulated by the vehicle unit 14 in the absence of the mobile unit 16. This information is transmitted by the mobile unit 16 to the server 22 and is flagged as operation of the vehicle 12 without the mobile unit 16. For example, it is anticipated that exact location of the vehicle 12 in the absence of the mobile unit 16 would not be known. Therefore, it would not be known exactly where the vehicle 12 was driven during the trips without the mobile unit 16. It is anticipated that a certain level of driving without the presence of the mobile unit 16 would be acceptable to the insurance server 24; however, certain amounts of distances driven or the percentage of distance driven without the presence of the mobile unit 16 might increase the rate of insurance on insurance server 24 or disqualify the user from a monitored insurance rate based program.

Each time the mobile unit 16 disconnects from the vehicle unit 14 (such as when the user leaves the vehicle 12 and/or when the engine is turned off), the mobile unit 16 and the vehicle unit 14 each store the last odometer and the last location of the vehicle 12. This information can be used by the mobile unit 16 to determine whether the vehicle 12 was moved in the absence of the mobile unit 16. Further, this information can be used to find the vehicle 12, such as in a large parking lot. On the mobile unit 16, the user can select an option to recall the last known location of the vehicle 12 and be guided (such as by arrows and distances or headings and distances) to the last known location of the vehicle 12.

Additionally, if the vehicle 12 is driven without the mobile unit 16, the vehicle unit 14 can propagate its position using the stored last location as a starting point and using its speed and odometer information (for distance) and three-axis accelerometer 36 (for heading). This information can be used to generate a rough trip history, which may be sufficient to indicate a general location to which the vehicle 12 was driven. For example, it may be sufficient to determine that the vehicle 12 has been driven to a region with a different insurance rate level. Or, if the vehicle 12 is stolen, this information can be transmitted from the vehicle 12 to the server 22 (upon request from the server) to assist in locating the stolen vehicle 12.

Referring once again to FIG. 1, the system 10 can also function as a speed probe for a traffic monitoring system (while simultaneously meeting the purposes described above or not). As a speed probe, the speed and location of many vehicles 12 is transmitted by their systems 10 to the server 22. Current speed probes use cell tower triangulation to estimate car speed and hence traffic conditions; others may use GPS to do the same. Both are inaccurate and erroneous as traffic estimation can be erroneously computed due to pedestrian cell phones or in parked cars, or people riding bicycles and carrying cell phones. With the present invention, the system 10 obtains actual speed from the vehicle 12 (from vehicle bus 18), which is much more accurate than the cell tower triangulation. Also, the system 10 provides GPS location, which is also more accurate, but even if the location is based upon cell tower based estimated location, at least there is no doubt that the speed information is from a vehicle 12 and not just from a pedestrian or bicyclist cell phone. The server 22 obtains data unobtrusively from many systems 10 in many vehicles 12, maps their locations and speeds onto roadways to compile traffic maps.

In accordance with the provisions of the patent statutes and jurisprudence, exemplary configurations described above are considered to represent a preferred embodiment of the invention. However, it should be noted that the invention can be practiced otherwise than as specifically illustrated and described without departing from its spirit or scope. 

1. A method of monitoring a vehicle including the steps of: a) associating a mobile device with a vehicle; b) determining a location of the mobile device; and c) determining a cost of insurance for the vehicle based upon said step b).
 2. The method of claim 1 wherein the mobile device includes a GPS receiver.
 3. The method of claim 1 wherein the mobile device includes a cell phone.
 4. The method of claim 3 wherein said step b) is performed by cell tower triangulation of the cell phone.
 5. The method of claim 1 wherein the mobile device collects vehicle operating data from the vehicle.
 6. The method of claim 5 further including the step of analyzing the vehicle operating data.
 7. The method of claim 6 wherein said step c) is performed at least in part based upon the vehicle operating data.
 8. The method of claim 7 wherein said step c) is performed at least in part based upon the analysis of the vehicle operating data.
 9. The method of claim 6 wherein the mobile device performs the step of analyzing the vehicle operating data.
 10. The method of claim 9 wherein the mobile device transmits the analysis of the vehicle operating data to a remote server and wherein the remote server performs said step c) based upon the analysis of the vehicle operating data.
 11. The method of claim 5 wherein the vehicle operating data includes speed of the vehicle.
 12. The method of claim 5 wherein the vehicle operating data includes distance traveled by the vehicle.
 13. A method of monitoring operation of a vehicle including the steps of: a) associating a mobile device with the vehicle; b) monitoring the operation of the vehicle with the mobile device; c) recording operation of the vehicle on the vehicle when the vehicle is operated without the mobile device present; and d) detecting an occurrence of operation of the vehicle without the mobile device present.
 14. The method of claim 13 wherein said step c) includes the step of recording distance traveled by the vehicle while the mobile device is not present.
 15. The method of claim 14 further including the step of communicating to the mobile device the recorded distance traveled by the vehicle without the mobile device present.
 16. The method of claim 15 further including the step of determining a cost of insurance based upon the operation of the vehicle monitored in said step b) and based upon the operation of the vehicle recorded in said step c).
 17. The method of claim 13 wherein said step d) includes the step of recording an odometer of the vehicle on the mobile device and subsequently comparing the recorded odometer on the mobile device to the odometer of the vehicle.
 18. The method of claim 13 wherein said step d) further includes the step of recording a last location where the vehicle last communicated with the mobile device and comparing the last location to a new location where the vehicle communicates with the mobile device.
 19. The method of claim 13 further including the step of transmitting the recorded operation of the vehicle via the mobile device to server.
 20. A method of monitoring a vehicle including the steps of: a) determining that a mobile device is near the vehicle; b) determining a location of the mobile device; and c) determining a location of the vehicle based upon said steps a-b).
 21. The method of claim 20 wherein said mobile device includes a cell phone.
 22. The method of claim 20 wherein said mobile device includes a GPS receiver.
 23. The method of claim 20 further including the steps of: d) storing the location of the vehicle on the mobile device; e) determining that the mobile device is no longer near the vehicle; and f) after said step e), indicating the stored location of the vehicle to a user on the mobile device.
 24. The method of claim 20 further including the step of determining a cost of insurance based upon said step c).
 25. The method of claim 20 further including the step of receiving on the mobile device vehicle operating data from the vehicle.
 26. The method of claim 20 further including the steps of: d) storing the vehicle location on the mobile device as a last vehicle location; e) comparing the last vehicle location to a new vehicle location where the vehicle reestablishes communication with the mobile device; and f) determining whether the vehicle has been moved without the mobile device based upon said step e).
 27. The method of claim 20 further including the step of determining that the vehicle has been operated without the presence of the mobile device.
 28. The method of claim 20 further including the step of: sending vehicle speed information and the location of the vehicle to a server.
 29. The method of claim 28 further including the step of accumulating vehicle speed information and vehicle location from a plurality of vehicles, including the vehicle, in order to compile traffic information.
 30. A vehicle monitoring device comprising: a vehicle unit for installation in a vehicle, the vehicle unit programmed to be associated with at least one mobile device and to transmit vehicle operating data via the mobile device.
 31. The device of claim 30 wherein the vehicle unit includes a GPS receiver.
 32. The device of claim 30 wherein the vehicle unit includes a cell phone.
 33. The device of claim 30 wherein the vehicle unit includes an accelerometer.
 34. The device of claim 30 wherein the vehicle unit collects the vehicle operating data from the vehicle including speed and odometer.
 35. The device of claim 33 wherein the vehicle unit analyzes the vehicle operating data.
 36. The device of claim 30 wherein the vehicle unit is programmed to receive location information from the mobile device.
 37. The device of claim 30 wherein the vehicle unit stores a last location received from the mobile device after a connection with the mobile device is lost.
 38. The device of claim 37 wherein the vehicle unit records distance traveled by the vehicle when the mobile device is not present.
 39. A mobile device for monitoring a vehicle comprising, wherein the mobile device is programmed to: determine that the mobile device is near a vehicle; determine a location of the mobile device; and monitor operation of the vehicle based upon a determination that the mobile device is near the vehicle and based upon the location of the mobile device.
 40. The mobile device of claim 39 including a cell phone.
 41. The mobile device of claim 39 further including a GPS receiver.
 42. The mobile device of claim 39 wherein the mobile device is programmed to: store a location of the vehicle on the mobile device; determine that the mobile device is no longer near the vehicle; and while the mobile device is not near the vehicle, indicate the stored location of the vehicle to a user on the mobile device.
 43. The mobile device of claim 39 wherein the mobile device is programmed to receive vehicle operating data from the vehicle.
 44. The mobile device of claim 39 wherein the mobile device is programmed to: store the vehicle location on the mobile device as a last vehicle location; compare the last vehicle location to a new vehicle location where the vehicle reestablishes communication with the mobile device; and determine whether the vehicle has been moved without the mobile device based upon the comparison.
 45. The mobile device of claim 39 wherein the mobile device is programmed to determine that the vehicle has been operated without the presence of the mobile device.
 46. The mobile device of claim 39 wherein the mobile device is programmed to send vehicle speed information and the location of the vehicle to a server.
 47. A computer readable medium storing instructions which when executed by a mobile computing device perform the steps of: a) determining that the mobile computing device is near an associated vehicle; b) determining a location of the mobile computing device; and c) determining a location of the vehicle based upon said steps a-b).
 48. The computer readable medium of claim 47 further storing instructions which when executed by the mobile computing device perform the step of: d) monitoring the location of the vehicle based upon said steps a-c); and e) transmitting the location of the vehicle wirelessly to a remote server.
 49. The computer readable medium of claim 47 further storing instructions which when executed by the mobile computing device perform the step of: d) transmitting the location of the vehicle wirelessly to a remote server. 